Introducing the TrustTheVote Project and Blog

Our thanks go to our patient readers for a bit of radio silence while we've been standing up the TrustTheVote project, and infrastructure for it such as a blog, wiki, source code repository, and project tracker.

TrustTheVote at Golden Gate Ruby Conference

I had been meaning to report on OSDV's visit to the Golden Gate Ruby Convention, where Greg presented on the TrustTheVote project. But instead TTV developer Chad Wooley has already done a much better than I could do, reporting on GoGaRuCo in his blog. Thank you Chad!

Which Accessible Voting "Model"? ... All of the Above

Continuing the story of accessible voting and the "we just build stuff" mantra of the TrustTheVote project, I have an example of a serious mis-understanding that can easily arise because of the jargon and procedural confusion I wrote about earlier.

Five Ways to Call a Voting Machine a ...

Today I have an excellent example of how important it is, and sometimes difficult, to maintain clarity around the technology that we're building in the TrustTheVote project, and what we are (and are not) doing in OSDV generally. This particular example illustrates how voting technology is already bedeviled by jargon, inconsistent terminology, and procedural confusion -- so that terminology and explanation that work for one group of people just don't work elsewhere.

Last 2008 Lessons Learned: Election Transparency

Election transparency was the third lessons-learned topic from the RSA panel that I wrote about earlier.  As in the other two lessons learned, the Humboldt County Transparency Project is a great example, but here are two more, to show the small and the huge ends of the scale.

RSA Conference: More 2008 Election Tech Lessons Learned - Auditing

Election audit was the second lessons-learned topic from the RSA panel that I wrote about earlier.  I illustrate with two examples.

RSA Conference Panel: Lessons Learned from 2008 Election Technology

I spoke in a panel at the RSA Conference yesterday, on the topic of lessons learned in 2008 about voting technology. I thought I'd use this blog to share my remarks, but even though we each spoke for only 5 minutes before the question and answer period, I covered three areas of lessons learned; so I'll cover them in separate blog posts on each topic of (1) Usability lessons (2) Audit lessons (3) Transparency lessons.

E-voting and Insider Threats: e-Election Fraud?

I found a remarkably good, plain-English description of the insider threats of digital voting systems, and with an intriguing title: Computer Experts Warn of Sophisticated Dagdag Bawas with Automated Polls.

Mixed Bag: Voting System Vendors' Rhetoric on Open Source

The current voting system vendors recently released a paper on election technology and open source. As a pleasant surprise, it is a mixed bag, in that much of the report's rhetoric is  asspecious as previously seen, but there are also signs of the vendors taking steps towards comprehending what the voting system market would be like, with open source digital voting technology.

More Humbolt Election Tech Weirdness: Premier Huffs

Well, I am sorry to say that I have to make an exception to my avoidance of casting voting system vendors in a bad light -- in this case Premier Systems (formerly Diebold). I was rather proud of PS(fD) when they owned up to the "ballot dropping" software problem (paper ballots scanned and apparently counted, but the first few not actually counted, and no log record of the deletion) that was discovered in the post-election audit conducted in Humboldt County by registrar Categories:

• digital voting
• e-voting
• humboldt
• premier
• transparency

• jsebes's blog
• Add new comment
• Read more
• 158 reads